Your data has issues
There is a problem
- 17 ‘plan’ fields do not match the ‘reference’ field in the plan dataset
| Reference | Plan | Plan event | Event date | Actual date | Entry date | Notes |
|---|---|---|---|---|---|---|
| city-of-york-council-local-plan-2017-reg-19-publication-local-plan-published |
city-of-york-council-local-plan-2017 Missing associated entity |
reg-19-publication-local-plan-published | 2018-02-21 | 2018-02-21 | 2026-03-30 | |
| city-of-york-council-local-plan-2017-submit-plan-for-examination |
city-of-york-council-local-plan-2017 Missing associated entity |
submit-plan-for-examination | 2018-05-25 | 2018-05-25 | 2026-03-30 | |
| city-of-york-council-local-plan-2017-planning-inspectorate-found-sound |
city-of-york-council-local-plan-2017 Missing associated entity |
planning-inspectorate-found-sound | 2025-02-14 | 2025-02-14 | 2026-03-30 | |
| city-of-york-council-local-plan-2017-plan-adopted |
city-of-york-council-local-plan-2017 Missing associated entity |
plan-adopted | 2025-02-27 | 2025-02-27 | 2026-03-30 | |
| city-of-york-council-local-plan-2017-timetable-published |
city-of-york-council-local-plan-2017 Missing associated entity |
timetable-published | 2025-04-01 | 2025-04-01 | 2026-03-30 | |
| city-of-york-council-new-local-plan-publish-notice-intention-commence |
city-of-york-council-new-local-plan Missing associated entity |
publish-notice-intention-commence | 2026-07-31 | 2026-07-31 | 2026-07-31 | Notice published initially on 26-06-2026 and reissued on 31-07-2026 |
| city-of-york-council-new-local-plan-scoping-consultation-start |
city-of-york-council-new-local-plan Missing associated entity |
scoping-consultation-start | 2026-08-31 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-scoping-consultation-end |
city-of-york-council-new-local-plan Missing associated entity |
scoping-consultation-end | 2026-10-12 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-gateway-1-self-assessment |
city-of-york-council-new-local-plan Missing associated entity |
gateway-1-self-assessment | 2026-11-30 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-plan-content-evidence-consultation-start |
city-of-york-council-new-local-plan Missing associated entity |
plan-content-evidence-consultation-start | 2027-07-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-plan-content-evidence-consultation-end |
city-of-york-council-new-local-plan Missing associated entity |
plan-content-evidence-consultation-end | 2027-09-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-gateway-2-advice-sought |
city-of-york-council-new-local-plan Missing associated entity |
gateway-2-advice-sought | 2027-11-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-proposed-plan-consultation-start |
city-of-york-council-new-local-plan Missing associated entity |
proposed-plan-consultation-start | 2028-07-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-proposed-plan-consultation-end |
city-of-york-council-new-local-plan Missing associated entity |
proposed-plan-consultation-end | 2028-08-31 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-gateway-3-advice-sought |
city-of-york-council-new-local-plan Missing associated entity |
gateway-3-advice-sought | 2028-10-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-examination-submitted |
city-of-york-council-new-local-plan Missing associated entity |
examination-submitted | 2029-01-01 | 2026-07-31 | ||
| city-of-york-council-new-local-plan-adopted |
city-of-york-council-new-local-plan Missing associated entity |
adopted | 2029-05-01 | 2026-07-31 |
How to fix this issue
Your data is missing a plan.
The plan timetable guidance explains how to fix the issue:
plan
This is the unique reference for your overall plan. For example:
- LP-BRX-2024
- barnet-local-plan-2021-2036
- hertfordshire-minerals-and-waste-plan
- essex-minerals-plan
- essex-waste-plan
- county-durham-supplementary-plan
The ‘plan’ field in your plan timetable dataset must match the ‘reference’ field from your plan dataset.
How to improve City of York Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL